Are you using a standalone WAS proxy? If so, why introduce a single point of failure? I have always added a WAS proxy on the same node as the meeting server, that way you have two (or more) WAS proxies that can redirect to the application should one fail. If standalone is preferred then surely you should have two of them on separate nodes?
Do you have an equal spread of apps servers on both server002 and 003? Do you have Advanced, Meetings and STProxy on both?
Any way. DNS for whatever you want to use the WAS proxy for should point to server004. It should not point to server002 or 003.
You
do need to use a WAS proxy with a cluster of meeting servers.
You
do not need to use a WAS proxy for a cluster of STAdvanced and/or STProxy but you can if you want. If not, you should have a load balancer handle that. A load balancer will probably provide better performance and scalability.
Load balancer notes
With Proxy, once you get placed on a node you should stay with that node unless it fails.
For Advanced, Proxy and Meetings, it is recommended to be 60 sec or longer. Setting the persistent connections on the load balancer depends on the type of load balancer being used.
If using Persistent Big F5 Load Balancer, it may be configured for affinity and there is a cookie based affinity that should work well.
You will need to manage things with virtual hosts. The WAS proxy is aware of the whole cell so will manage all your applications so you should control it using virtual hosts.
This technote
http://www-01.ibm.com/support/docview.wss?uid=swg21515598 details how to set up virtual hosts for STProxy and meetings. It is also detailed in the knowledge center
http://www-01.ibm.com/support/knowledgecenter/SSKTXQ_9.0.0/admin/config/config_meet_virtual_host.dita. You should create a virtual host for STProxy if you haven't done so already.
The following technote is similar to the one above but explains problems when STAdvanced and meetings are in the same cell. It is pretty much the same as the previous technote
http://www-01.ibm.com/support/docview.wss?uid=swg21571842
Sort out the virtual hosts and report back with screen shots of your virtual hosts settings and whether the situation has improved.
Also, consider you are running three apps servers on one node, all of which want to use port 80. In this case are you proposing to use the WAS proxy as the port 80 entry point and allowing the apps servers to operate on their own WC* ports which are not 80 and 443?
Return to top
. . RE: Clustering v9 Meetings with sta... (~Kim Opniman 11.Sep.14) 
Print this page
